With few exceptions, data groups must be defined in a device template file in order for them to be available for use on a remote device. Which data groups are defined by a device template file depends on protocol, device type, and unique configuration.
CygNet distributes sample device template files for its EIEs, each of which typically serves one or more hardware models along with applicable firmware. Therefore, the data groups described below are only those data groups defined by CygNet in sample device template file(s). Your template(s) might not include some of the data groups described below. Device template files exist to enable users to customize device configurations; however, CygNet is not responsible for changes made by users.
For information about data group definitions and device template files, see Device Template Files.
For more information about data group dependencies, see Data Group Dependencies.
Note: In data groups in edit mode, a Send only edited items check box displays on the View Data dialog box, and when checked, only the edited values are written to the DDS transaction.
Browse by letter: A C D E G H M P R S
| Data Group Type | Usage Notes |
|---|---|
|
"Audit Trail" returns all history for all meters. |
|
|
"Configurable Modbus" |
|
|
CfgPt |
"Configurable Points" |
|
"Date/Time" |
|
|
DiagMsg |
"Diagnostic Message" |
|
"Event Report" |
|
|
"FMS Legacy Config Send Data" is used to send modified measurement data to the field device. This data group is required only if you plan to use FMS and want to perform this specific task. |
|
|
"FMS Legacy Configuration Data" receives data from Meter Run Data. |
|
|
"FMS Legacy Events Data" receives data from Audit Trail. Uses the previously retrieved transaction if the data range is sufficient. Specify date ranges on a per-data group basis within the device editor. For more information, see Selecting Date and Time. |
|
|
"FMS Legacy History Data" receives data from History Hourly data groups. Uses the previously retrieved transaction if the data range is sufficient. Specify date ranges on a per-data group basis within the device editor. For more information, see Selecting Date and Time. |
|
|
"History Daily Cone" |
|
|
"History Daily Liquid" |
|
|
"History Daily Orifice" |
|
|
"History Daily Turbine" |
|
|
HistGq01 |
"History Gas Quality Src 1" |
|
HistGq02 |
"History Gas Quality Src 2" |
|
"History Hourly Cone" |
|
|
"History Hourly Liquid" |
|
|
"History Hourly Orifice" |
|
|
"History Hourly Turbine" |
|
|
HistPV |
"History PV" |
|
"Meter Run Data" |
|
|
ModTest1 |
"MODBUS Sample 1" |
|
ModTest2 |
"MODBUS Sample 2" |
|
"Table 01 - AI" |
|
|
"Table 02 - DI" |
|
|
"Table 03 - DO" |
|
|
"Table 04 - AO" |
|
|
"Table 13 - Supervisory" |
|
|
"Table 14 - AI(2)" |
|
|
"Table 15 - DI(2)" |
|
|
PointTbl38 |
"Table 38 - Cone" |
|
PointTbl39 |
"Table 39 - Energy Calculation" |
|
PointTbl41 |
"Table 41 - Orifice" |
|
PointTbl42 |
"Table 42 - Turbine" |
|
PointTbl43 |
"Table 43 - Liquid" |
|
PointTbl61 |
"Table 61" |
|
PointTbl99 |
"Table 99 - System Events" |
|
"RTU Config" A valid RTU Config must be retrieved before other data groups can be retrieved or sent. |
|
|
"Single Modbus Register" |
|
|
"Single Point" |
|
|
|
